Skip to content

Conversation

averykatko
Copy link

@averykatko averykatko commented Sep 23, 2025

sorry I originally had an actually reasonable commit history for awesome_owl but I messed something up in the switch... oops 🫠

@robodoo
Copy link

robodoo commented Sep 23, 2025

Pull request status dashboard

@cgun-odoo cgun-odoo self-requested a review September 25, 2025 15:18
Copy link

@cgun-odoo cgun-odoo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey there 👋 nice job 🥇

slots: {
type: Object,
shape: {
default: true,

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this is useless, can you delete it and see if it changes anything?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yep, it complains if I remove slots entirely but it's fine without having the shape specified 1771dde

Comment on lines 12 to 15
// shape: {
// id: String,
// description: String,
// },

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Don't have commented out code on your commits. If you want to keep history, you already have your commit history.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also this looks like something you could use why is it commented out 😆

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this gave me a prop validation error because there were additional fields beyond id and description passed as props so I was gonna look into how to handle that correctly..

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

adding "*" into shape makes it work: da104d4

};

setup() {
console.log("setup dialog");

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Remove all console.log and print statements before you commit

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

6c5926d

(this would've been caught by pre-commit hooks probably? In real-world PRs if this got in somehow would we want to amend the commit and force-push or just fix it in a subsequent commit?)

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think the best flow is

  • You push a commit and create a PR
  • Someone reviews your PR and leaves comments
  • You fix the comments with subsequent commits (because at this point if you force push it's difficult for the reviewer to find what they commented on)
  • Reviewer approves
  • You squash your commits and merge

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

But what you said is correct this would be caught by pre-commit

Comment on lines 28 to 35
this.state = useState(
this.props.items.map(
item => ({
...item,
checked: !this.props.excludedItems.includes(item.id),
}),
),
);

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Here you're creating a state variable called state and it's value is the items list. A variable called state referring to an item list doesn't make much sense. Maybe you can do something like this.state = useState({itemList: lblalbal});

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

slots: {
type: Object,
shape: {
default: true,

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this doesn't do anything again. Try removing it

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

export class Counter extends Component {
static template = "awesome_owl.Counter";
static props = {
onChange: {type: Function, required: false},

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
onChange: {type: Function, required: false},
onChange: {type: Function, optional: true},

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

const config = {
dev: true,
name: "Owl Tutorial",
name: "Owl Tutorial"

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

whyyyyy

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this must've been something from how I recovered from losing my commit history in the move from 19.0 to 18.0 base branch by doing things in the wrong order

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Comment on lines +130 to +132

# vscode
.vscode/

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Don't push your changes on this file

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants