-
Notifications
You must be signed in to change notification settings - Fork 44
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add additional wireless settings #1602
Add additional wireless settings #1602
Conversation
For consistency with the rest of the network settings.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In general it looks good, just a few comments. Thanks!
@@ -164,6 +164,66 @@ | |||
"mesh", | |||
"ap" | |||
] | |||
}, | |||
"hidden": { | |||
"title": "Indicates that the wifi network is not broadcasting it's SSID", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should it be "wifi", "Wi-Fi", wireless... In this schema we have been using "wireless" but we can change it. Just for consistency.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think wireless
is fine. I changed the descriptions accordingly.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OK, we will plan for that.
#[error("Invalid group algorithm: {0}")] | ||
pub struct InvalidGroupAlgorithm(String); | ||
|
||
impl FromStr for GroupAlgorithm { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For some time, I have been thinking whether we should use strum (see the EnumString example) to avoid all those trivial conversions.
I am not sure about how error handle would be, but I think it is worth having a closer look.
In any case, it is out of the scope of this PR.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Totally agree, strum would make this a lot simpler 🙂
let group_algorithms: Vec<GroupAlgorithm> = group_algorithms | ||
.get() | ||
.iter() | ||
.map(|x| x.downcast_ref::<str>().unwrap()) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Those unwraps
are dangerous because is something goes wrong, the whole service would go down. Perhaps you might want to split this chain into smaller functions.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is the testing code. The code for the service does use the proper error handling.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ouch, Friday afternoon, you know 😅
let group_algorithms: Vec<GroupAlgorithm> = group_algorithms | ||
.get() | ||
.iter() | ||
.map(|x| x.downcast_ref::<str>().unwrap()) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ouch, Friday afternoon, you know 😅
Prepare for releasing Agama 10· * #1263 * #1330 * #1407 * #1408 * #1410 * #1411 * #1412 * #1416 * #1417 * #1419 * #1420 * #1421 * #1422 * #1423 * #1424 * #1425 * #1428 * #1429 * #1430 * #1431 * #1432 * #1433 * #1436 * #1437 * #1438 * #1439 * #1440 * #1441 * #1443 * #1444 * #1445 * #1449 * #1450 * #1451 * #1452 * #1453 * #1454 * #1455 * #1456 * #1457 * #1459 * #1460 * #1462 * #1464 * #1465 * #1466 * #1467 * #1468 * #1469 * #1470 * #1471 * #1472 * #1473 * #1475 * #1476 * #1477 * #1478 * #1479 * #1480 * #1481 * #1482 * #1483 * #1484 * #1485 * #1486 * #1487 * #1488 * #1489 * #1491 * #1492 * #1493 * #1494 * #1496 * #1497 * #1498 * #1499 * #1500 * #1501 * #1502 * #1503 * #1504 * #1505 * #1506 * #1507 * #1508 * #1510 * #1511 * #1512 * #1513 * #1514 * #1515 * #1516 * #1517 * #1518 * #1519 * #1520 * #1522 * #1523 * #1524 * #1525 * #1526 * #1527 * #1528 * #1529 * #1530 * #1531 * #1532 * #1533 * #1534 * #1535 * #1536 * #1537 * #1540 * #1541 * #1543 * #1544 * #1545 * #1546 * #1547 * #1548 * #1549 * #1550 * #1552 * #1553 * #1554 * #1555 * #1556 * #1557 * #1558 * #1559 * #1560 * #1562 * #1563 * #1565 * #1566 * #1567 * #1568 * #1569 * #1570 * #1571 * #1572 * #1573 * #1574 * #1575 * #1576 * #1577 * #1578 * #1579 * #1580 * #1581 * #1583 * #1584 * #1585 * #1586 * #1587 * #1588 * #1589 * #1590 * #1591 * #1592 * #1593 * #1596 * #1597 * #1598 * #1600 * #1602 * #1605 * #1606 * #1607 * #1608 * #1610 * #1611 * #1612 * #1613 * #1614 * #1619 * #1620 * #1621
https://build.opensuse.org/request/show/1202589 by user IGonzalezSosa + anag+factory - Version 10 - Change the license to GPL-2.0-or-later (gh#agama-project/agama#1621). - Expose the zFCP D-Bus API through HTTP (gh#agama-project/agama#1570). - For CLI, use HTTP clients instead of D-Bus clients, final piece: Storage (gh#agama-project/agama#1600) - added StorageHTTPClient - Add additional wireless settings (gh#agama-project/agama#1602).
Problem
Network model was missing some required fields for the wicked migration.
Solution
Added the required fields to both the model and settings. I've also added some fields present in the model to be available via the settings.
Testing