Closed youyingfeng closed 4 years ago
Most of my work has been either adding additional fields to existing classes or integrating pull requests, and the only thing worthy of a DG entry is the user interface. Am I allowed to explain the user interface for the DG assignment?
Sure. You can also explain things you plan to implement later (if any), the proposed implementation for a feature that someone else can add in the future, alternative designs to consider etc.
Alternatively, would it be wise to include designs for potential features that the team doesn't plan to add for this semester, but would be useful for, say, v2.0
? This is an approach that the AddressBook-3 Developer Guide uses.
Alternatively, would it be wise to include designs for potential features that the team doesn't plan to add for this semester, but would be useful for, say,
v2.0
? This is an approach that the AddressBook-3 Developer Guide uses.
Yes, especially if you don't have enough DG content to showcase your DG writing skills.
I assume this issue has been resolved. Feel free to reopen if not.
Most of my work has been either adding additional fields to existing classes or integrating pull requests, and the only thing worthy of a DG entry is the user interface. Am I allowed to explain the user interface for the DG assignment?