You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think it would be useful if there was a generic method of inheriting values from other configuration blocks. This is already implemented by various tags already (connect classes, oper classes/types, etc) but it would a lot less duplication if this was available at the parser level. Some ideas for how this could be implemented have been mentioned below.
SadieCat
changed the title
[Proposal] Method of inheriting configuration values from other keys.
[RFC] Method of inheriting configuration values from other keys.
Jun 6, 2014
I vote option 1, because I wouldn't want increased complexity, even if slight, because the InspIRCd config itself is already hard to many beginners and we don't need something as simple (or complex, depending on what you do with it) as connect classes being the thing that pushes them away.
01:08:21 AM <+Techman> I like the current system
01:09:05 AM <+Techman> Anything not specified that has a parent="" also in the tag are options that should be inherited imo
I think it would be useful if there was a generic method of inheriting values from other configuration blocks. This is already implemented by various tags already (connect classes, oper classes/types, etc) but it would a lot less duplication if this was available at the parser level. Some ideas for how this could be implemented have been mentioned below.
Normal
Points for
Points against
Namespaced Attributes
Points for
Points against
Namespaced Elements
Points for
Points against
The text was updated successfully, but these errors were encountered: