Differentiate Module and Object level fields in Module definition #86

Open
opened 2024-01-02 20:19:14 +01:00 by Aire-One · 0 comments
Owner

Currently, Module and Object level fields are mixed up in the Record definition. We should separate them.

Example:

  • wibox, as a Module has a field widget that is a reference to the wibox.widget Module.
  • A wibox instance has a widget field that is the wibox's content.

Both fields share the same name and shouldn't be mixed because their types aren't exactly the same thing.

Also, we don't want Teal to hint fields that aren't part of the currently manipulated resource.

Currently, Module and Object level fields are mixed up in the Record definition. We should separate them. Example: - `wibox`, as a Module has a field `widget` that is a reference to the `wibox.widget` Module. - A `wibox` instance has a `widget` field that is the wibox's content. Both fields share the same name and shouldn't be mixed because their types aren't exactly the same thing. Also, we don't want Teal to hint fields that aren't part of the currently manipulated resource.
Sign in to join this conversation.
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: Aire-One/awesomewm.d.tl#86
No description provided.