Currently nhaystack is using the prefix "ax" for Niagara specific "special" tags such as axSlotPath. This tag is of course derived from Niagara AX. Given that there is now an open proposal to add new Niagara specific tags such as axOverridden I would like to revisit the design of using "ax". My main concern is that eventually we will port this Niagara 4 (and maybe 5, 6, etc :) But we'll definitely want to keep backward compatibility, so using "ax" might be confusing.
I would like to propose a breaking change from using the "ax" prefix to just the "n" prefix. So then we'd have "nSlotPath" instead of "axSlotPath", "nOverride" versus "axOverride".
Although personally I do like the look of "ax" better and I don't really like a breaking change. But does seem like something worthy of a discussion...
Mike JarmyWed 14 May 2014
After thinking about this for a while, I think I'd rather just leave "ax" as the prefix. I don't really want to introduce a breaking change, because I think that the NHaystack user community is probably already using the "ax" tags in production, so it would cause a headache for people.
It would have been better had I chosen a more neutral prefix in the first place, but I think we can fix this just by documenting that "ax" means a Niagara-specific tag, regardless of whether its N4 or whatever. I will add a section to the naystack documentation explaining how all the "ax" tags work.
Brian FrankWed 14 May 2014
I'm ok with - at least now we are doing it consciously :)
Brian Frank Mon 12 May 2014
Currently nhaystack is using the prefix "ax" for Niagara specific "special" tags such as
axSlotPath. This tag is of course derived from Niagara AX. Given that there is now an open proposal to add new Niagara specific tags such asaxOverriddenI would like to revisit the design of using "ax". My main concern is that eventually we will port this Niagara 4 (and maybe 5, 6, etc :) But we'll definitely want to keep backward compatibility, so using "ax" might be confusing.I would like to propose a breaking change from using the "ax" prefix to just the "n" prefix. So then we'd have "nSlotPath" instead of "axSlotPath", "nOverride" versus "axOverride".
Although personally I do like the look of "ax" better and I don't really like a breaking change. But does seem like something worthy of a discussion...
Mike Jarmy Wed 14 May 2014
After thinking about this for a while, I think I'd rather just leave "ax" as the prefix. I don't really want to introduce a breaking change, because I think that the NHaystack user community is probably already using the "ax" tags in production, so it would cause a headache for people.
It would have been better had I chosen a more neutral prefix in the first place, but I think we can fix this just by documenting that "ax" means a Niagara-specific tag, regardless of whether its N4 or whatever. I will add a section to the naystack documentation explaining how all the "ax" tags work.
Brian Frank Wed 14 May 2014
I'm ok with - at least now we are doing it consciously :)